Summary

Cuts ~400-500ms off GET /api/0/projects/{org}/{project}/ by asking the server to skip full-org serialization. The collapsed response carries only {id, slug} for organization instead of the full payload (feature flags, options, etc).

Colleague flagged this optimization noting the UI already benefits — every CLI hot path that fetches project details can ride the same win.

Hot paths that benefit

• DSN auto-detect (numeric orgId/projectId → slug resolution)
• Explicit <org>/<project> target validation in resolveTarget
• findProjectsBySlug (one getProject per accessible org, multiplying the saving)
• project view, project delete, dashboard create, release list, trace view, init, and others

All project detail fetches in the CLI funnel through getProject() in src/lib/api/projects.ts, so a single change covers everything.

Handling the trimmed response

The collapsed payload drops organization.name. Four call sites displayed it:

• src/lib/resolve-target.ts — three DSN resolution paths + one cache-seed after explicit target validation
• src/lib/dsn/resolver.ts — DSN → ResolvedProject
• src/lib/formatters/human.ts — project view's Organization: row

All now use a new resolveOrgDisplayName(orgSlug, explicitName?) helper with the fallback chain:

1. Explicit name if the server returned it (self-hosted / older Sentry ignore collapse and return the full payload — handled transparently)
2. getCachedOrganizations() lookup — populated on login and every org-fanout operation
3. Slug itself as last resort

The cosmetic "name → slug" degradation only surfaces on cold-cache + collapse-honoring server, which is vanishingly rare (every auth flow warms the cache).

JSON output shape stays stable

sentry project view --json previously returned the full organization object (including name, feature flags, options). Since getProject() now collapses the server response, project view gains a jsonTransform that re-hydrates organization.name via resolveOrgDisplayName() before serialization. Downstream agents and scripts that scrape .organization.name continue to see a value.

When the server returns name (self-hosted / ignores collapse), the transform preserves it as-is. When absent, it falls back through the cached org list to the slug. Feature flags and options are no longer returned — this is a deliberate tradeoff, as those fields aren't documented stable CLI output and dropping them is where the perf win comes from.

Response cache invalidation is now prefix-based

The response cache keys by full URL (including sorted query params via buildCacheKey/normalizeUrl). Pre-PR, invalidateCachedResponse(baseUrl) would match the cached entry exactly. Post-PR, cached entries live under baseUrl?collapse=organization, so an exact-match invalidation would silently miss — project delete → project view would serve pre-deletion data.

invalidateProjectCaches switches to invalidateCachedResponsesMatching (prefix sweep) to catch the collapsed variant plus any future query-param additions. The trailing slash on buildApiUrl output guarantees the prefix can't collide with sibling projects (projects/acme/frontend/ does not prefix-match projects/acme/frontend-old/).

Side effect: sub-resources like /projects/acme/frontend/keys/ and /projects/acme/frontend/trace-items/... also get swept on project delete. This is desirable — those children would 404 after the parent is gone anyway.

Tests

Added to test/lib/api-client.test.ts:

• getProject sends ?collapse=organization query parameter — asserts the outgoing URL carries the query param.
• getProject tolerates collapsed response missing organization.name — confirms no blow-up when name is absent.
• 4 resolveOrgDisplayName cases: explicit name wins / cache fallback / slug fallback / empty-string falsy handling.

Added to test/lib/formatters/human.details.test.ts:

• falls back to org slug when collapsed response omits name — module-level useTestConfigDir ensures an empty org_regions table, regex-match asserts the slug appears in both the display-name and parens positions (stray cached name would fail).

Added to test/commands/project/view.func.test.ts:

• JSON output re-hydrates organization.name when API response omits it — exercises the new jsonTransform slug-fallback path.
• JSON output preserves organization.name when API response includes it — self-hosted / older-Sentry compat.
• JSON output still strips detectedFrom (human-only field) — regression guard for the jsonExclude → jsonTransform switch.
• JSON output honours --fields filter — confirms field filtering still works on top of the transform.

Verification

• bun run typecheck ✓
• bun run lint ✓ (only a pre-existing unrelated warning)
• bun run test:unit → 5676 pass / 0 fail (+4 new from follow-up)
• bun run test:isolated → 138 pass / 0 fail

Follow-ups (out of scope)

• Team detail (retrieveATeam) has the same ?collapse=organization support per the SDK types — same perf win available for team list etc.
• Similar-shape audit on other endpoints returning nested org payloads.